Tested with our company enterprise where we try to configure code security programmatically.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.45%. Comparing base (5458fbc) to head (30227e6).
⚠️ Report is 1 commits behind head on master.

@@           Coverage Diff           @@
##           master    #3920   +/-   ##
=======================================
  Coverage   92.45%   92.45%           
=======================================
  Files         203      203           
  Lines       14954    14954           
=======================================
  Hits        13826    13826           
  Misses        926      926           
  Partials      202      202           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Thank you, @tstollin. Please unit tests (either new or update existing ones) that demonstrate the inclusion of the new fields.

Thanks for the feedback @gmlewis. I've added a new unit test and the security_configuration_id field to the BypassReviewer. The new field is automatically added by GitHub in responses.
Regarding the unit test I'm not sure whether this suffices. If it does not, I would be grateful for any advice.

Unfortunately, I missed point 6. of "submitting a patch" in your https://github.com/google/go-github/blob/master/CONTRIBUTING.md and did force-pushes. :(
Is there any chance to salvage this PR?

Unfortunately, I missed point 6. of "submitting a patch" in your https://github.com/google/go-github/blob/master/CONTRIBUTING.md and did force-pushes. :( Is there any chance to salvage this PR?

It's OK... this is a relatively small PR, so no problem.
Force pushing makes it much more painful for reviewers when the PRs are larger... sometimes a review takes an hour or so, then after a force push, you can't see the changes "Since your last review" and you have to start over again.

Whups! I spoke too soon. Please run step 4 again and push the changes, and this should be good to go, @tstollin. Thank you.

Whups! I spoke too soon. Please run step 4 again and push the changes, and this should be good to go, @tstollin. Thank you.

oh, i ran the scripts but I missed the git add to include them in my commit. I've pushed them now. :)

Thank you, @tstollin and @alexandear!
Merging once tests pass.